Repository navigation
Update dependency react-i18next to v17.1.1 - #1560
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/react-i18next-17.x
branch
2 times, most recently
from
October 23, 2026 11:17
a080e24 to
9da7faa
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
17.1.0→17.1.1Release Notes
i18next/react-i18next (react-i18next)
v17.1.1Compare Source
componentsas an object with index keys, the component for key0is now rendered.components={{ 0: <a href={path} /> }}with"You're eligible. <0>Get started here.</0>"rendered the text without the link, a self-closing<0/>rendered nothing, and in<0>a <1>b</1></0>both elements were lost, while keys1and up and the array form worked. The object was passed on as the indexed children, so<0>resolved to the object itself. It is now looked up by key, like a named components map. This also fixes an arraycomponentsnext toreact.transDefaultProps.components, which the merge turns into such an object ({ Bold, 0, 1 }) and so lost its first entry, and a self-closing named tag in a mixed object ({ 0: <a />, Bold: <b /> }with<Bold/>), which rendered as the text<Bold />. Arrays, named maps and index objects starting at1render as before. Thanks @nk-batman21 (#1938).Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.